SherbyNet - /page/wikibook/entry.mu

Micron Document

`:top

In `F33f`_`[computer architecture`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Computer_architecture]`_`f, `!32-bit computing`! refers to computer systems with a `F33f`_`[processor`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Central_processing_unit]`_`f, `F33f`_`[memory`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Computer_memory]`_`f, and other major system components that operate on data in a maximum of 32-`F33f`_`[bit`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Bit]`_`f units.`:cite-ref-pcmprosise1995-1-0[`F5bf`_`[1`#cite-note-pcmprosise1995-1]`_`f]`:cite-ref-sdfebuchanan1997-2-0[`F5bf`_`[2`#cite-note-sdfebuchanan1997-2]`_`f] Compared to smaller bit widths, 32-bit computers can perform large calculations more efficiently and process more data per clock cycle. Typical 32-bit `F33f`_`[personal computers`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Personal_computer]`_`f also have a 32-bit `F33f`_`[address bus`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Address_bus]`_`f, permitting up to 4 `F33f`_`[GiB`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=GiB]`_`f of `F33f`_`[RAM`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Random-access_memory]`_`f to be accessed, far more than previous generations of system architecture allowed.`:cite-ref-3[`F5bf`_`[3`#cite-note-3]`_`f]

32-bit designs have been used since the earliest days of electronic computing, in experimental systems and then in large `F33f`_`[mainframe`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Mainframe_computer]`_`f and `F33f`_`[minicomputer`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Minicomputer]`_`f systems. The first hybrid 16/32-bit `F33f`_`[microprocessor`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Microprocessor]`_`f, the `F33f`_`[Motorola 68000`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Motorola_68000]`_`f, was introduced in the late 1970s and used in systems such as the original `F33f`_`[Apple Macintosh`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Apple_Macintosh]`_`f. Fully 32-bit microprocessors such as the `F33f`_`[HP FOCUS`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=HP_FOCUS]`_`f, `F33f`_`[Motorola 68020`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Motorola_68020]`_`f and `F33f`_`[Intel 80386`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=I386]`_`f were launched in the early to mid 1980s and became dominant by the early 1990s. This generation of personal computers coincided with and enabled the first `F33f`_`[mass-adoption of the World Wide Web`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=History_of_the_Internet]`_`f. While 32-bit architectures are still widely-used in specific applications, the PC and server market has moved on to `F33f`_`[64 bits`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=64-bit_computing]`_`f with `F33f`_`[x86-64`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=X86-64]`_`f and other 64-bit architectures since the mid-2000s with installed memory often exceeding the 32-bit address limit of 4 GiB on entry level computers. The latest generation of `F33f`_`[smartphones`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Smartphone]`_`f have also switched to 64 bits.

>>Contents

• `F0af`_`[Range for storing integers`#range-for-storing-integers]`_`f

• `F0af`_`[Technical history`#technical-history]`_`f

• `F0af`_`[Architectures`#architectures]`_`f

• `F0af`_`[Applications`#applications]`_`f

• `F0af`_`[Images`#images]`_`f

• `F0af`_`[File formats`#file-formats]`_`f

• `F0af`_`[See also`#see-also]`_`f

• `F0af`_`[References`#references]`_`f

• `F0af`_`[External links`#external-links]`_`f

-─

>>Range for storing integers

A 32-bit `F33f`_`[register`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Processor_register]`_`f can store 232 different values. The `F33f`_`[range`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Range_(computer_programming)]`_`f of `F33f`_`[integer`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Integer]`_`f values that can be stored in 32 bits depends on the `F33f`_`[integer representation`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Integer_(computer_science)]`_`f used. With the two most common representations, the range is 0 through `F33f`_`[4,294,967,295`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=4,294,967,295]`_`f (232 − 1) for representation as an (`F33f`_`[unsigned`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Signedness]`_`f) `F33f`_`[binary number`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Binary_number]`_`f, and −2,147,483,648 (−231) through `F33f`_`[2,147,483,647`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=2,147,483,647]`_`f (231 − 1) for representation as `F33f`_`[two's complement`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Two's_complement]`_`f.

One important consequence is that a processor with 32-bit `F33f`_`[memory addresses`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Memory_address]`_`f can directly access at most 4 `F33f`_`[GiB`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Gibibyte]`_`f of `F33f`_`[byte-addressable`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Byte_addressing]`_`f memory (though in practice the limit may be lower).

>>Technical history

The world's first stored-program `F33f`_`[electronic computer`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Electronic_computer]`_`f, the `F33f`_`[Manchester Baby`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Manchester_Baby]`_`f, used a 32-bit architecture in 1948, although it was only a `F33f`_`[proof of concept`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Proof_of_concept]`_`f and had little practical capacity. It held only 32 32-bit words of RAM on a `F33f`_`[Williams tube`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Williams_tube]`_`f, and had no addition operation, only subtraction.

Memory, as well as other digital `F33f`_`[circuits`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Electronic_circuit]`_`f and wiring, was expensive during the first decades of 32-bit architectures (the 1960s to the 1980s).`:cite-ref-4[`F5bf`_`[4`#cite-note-4]`_`f] Older 32-bit processor families (or simpler, cheaper variants thereof) could therefore have many compromises and limitations in order to cut costs. This could be a 16-bit `F33f`_`[ALU`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Arithmetic_logic_unit]`_`f, for instance, or external (or internal) buses narrower than 32 bits, limiting memory size or demanding more cycles for instruction fetch, execution or write back.

Despite this, such processors could be labeled `*32-bit`*, since they still had 32-bit registers and instructions able to manipulate 32-bit quantities. For example, the `F33f`_`[IBM System/360 Model 30`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=IBM_System/360_Model_30]`_`f had an 8-bit ALU, 8-bit internal data paths, and an 8-bit path to memory,`:cite-ref-5[`F5bf`_`[5`#cite-note-5]`_`f] and the original `F33f`_`[Motorola 68000`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Motorola_68000]`_`f had a 16-bit data ALU and a 16-bit external data bus, but had 32-bit registers and a 32-bit oriented instruction set. The 68000 design was sometimes referred to as `*16/32-bit`*.`:cite-ref-6[`F5bf`_`[6`#cite-note-6]`_`f]

However, the opposite is often true for newer 32-bit designs. For example, the `F33f`_`[Pentium Pro`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Pentium_Pro]`_`f processor is a 32-bit machine, with 32-bit registers and instructions that manipulate 32-bit quantities, but the external address bus is 36 bits wide, giving a larger address space than 4 GB, and the external data bus is 64 bits wide, primarily in order to permit a more efficient prefetch of instructions and data.`:cite-ref-7[`F5bf`_`[7`#cite-note-7]`_`f]

>>Architectures

Prominent 32-bit instruction set architectures used in general-purpose computing include the `F33f`_`[IBM System/360`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=IBM_System/360]`_`f, `F33f`_`[IBM System/370`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=IBM_System/370]`_`f (which had `F33f`_`[24-bit`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=24-bit_computing]`_`f addressing), `F33f`_`[System/370-XA`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=System/370-XA]`_`f, `F33f`_`[ESA/370`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=ESA/370]`_`f, and `F33f`_`[ESA/390`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=ESA/390]`_`f (which had `F33f`_`[31-bit`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=31-bit_computing]`_`f addressing), the `F33f`_`[DEC`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Digital_Equipment_Corporation]`_`f `F33f`_`[VAX`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=VAX]`_`f, the `F33f`_`[NS320xx`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=NS320xx]`_`f, the `F33f`_`[Motorola 68000 family`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Motorola_68000_family]`_`f (the first two models of which had 24-bit addressing), the `F33f`_`[Intel`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Intel]`_`f `F33f`_`[IA-32`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=IA-32]`_`f 32-bit version of the `F33f`_`[x86`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=X86]`_`f architecture, and the 32-bit versions of the `F33f`_`[ARM`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=ARM_architecture]`_`f,`:cite-ref-8[`F5bf`_`[8`#cite-note-8]`_`f] `F33f`_`[SPARC`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=SPARC]`_`f, `F33f`_`[MIPS`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=MIPS_architecture]`_`f, `F33f`_`[PowerPC`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=PowerPC]`_`f and `F33f`_`[PA-RISC`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=PA-RISC]`_`f architectures. 32-bit instruction set architectures used for embedded computing include the 68000 family and `F33f`_`[ColdFire`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=ColdFire]`_`f, x86, ARM, MIPS, PowerPC, and `F33f`_`[Infineon TriCore`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Infineon_TriCore]`_`f architectures.

>>Applications

On the `F33f`_`[x86 architecture`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=X86_architecture]`_`f, a 32-bit application normally means `F33f`_`[software`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Software]`_`f that typically (not necessarily) uses the 32-bit linear `F33f`_`[address space`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Address_space]`_`f (or `F33f`_`[flat memory model`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Flat_memory_model]`_`f) possible with the `F33f`_`[80386`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=80386]`_`f and later chips. In this context, the term came about because `F33f`_`[DOS`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=DOS]`_`f, `F33f`_`[Microsoft Windows`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Microsoft_Windows]`_`f and `F33f`_`[OS/2`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=OS/2]`_`f`:cite-ref-9[`F5bf`_`[9`#cite-note-9]`_`f] were originally written for the `F33f`_`[8088/8086`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Intel_8088]`_`f or `F33f`_`[80286`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Intel_80286]`_`f, `F33f`_`[16-bit`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=16-bit_computing]`_`f microprocessors with a `F33f`_`[segmented`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Memory_segment]`_`f address space where programs had to switch between segments to reach more than 64 `F33f`_`[kilobytes`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Kilobyte]`_`f of `F33f`_`[code`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Object_file]`_`f or data. As this is quite time-consuming in comparison to other machine operations, the performance may suffer. Furthermore, `F33f`_`[programming`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Computer_programming]`_`f with segments tend to become complicated; special `*far`* and `*near`* keywords or `*`F33f`_`[memory models`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=C_memory_model]`_`f`* had to be used (with care), not only in `F33f`_`[assembly language`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Assembly_language]`_`f but also in high level languages such as `F33f`_`[Pascal`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Pascal_programming_language]`_`f, compiled `F33f`_`[BASIC`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=BASIC]`_`f, `F33f`_`[Fortran`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Fortran]`_`f, `F33f`_`[C`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=C_(programming_language)]`_`f, etc.

The 80386 and its successors fully support the 16-bit segments of the 80286 but also segments for 32-bit address offsets (using the new 32-bit width of the main registers). If the `F33f`_`[base address`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Base_address]`_`f of all 32-bit segments is set to 0, and segment registers are not used explicitly, the segmentation can be forgotten and the processor appears as having a simple linear 32-bit address space. `F33f`_`[Operating systems`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Operating_system]`_`f like Windows or OS/2 provide the possibility to run 16-bit (segmented) programs as well as 32-bit programs. The former possibility exists for `F33f`_`[backward compatibility`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Backward_compatibility]`_`f and the latter is usually meant to be used for new `F33f`_`[software development`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Software_engineering]`_`f.`:cite-ref-10[`F5bf`_`[10`#cite-note-10]`_`f]

>>Images

In digital images/pictures, 32-bit usually refers to `F33f`_`[RGBA color space`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=RGBA_color_space]`_`f; that is, 24-bit `F33f`_`[truecolor`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=24-bit_color]`_`f images with an additional 8-bit `F33f`_`[alpha channel`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Alpha_channel]`_`f. Other image formats also specify 32 bits per pixel, such as `F33f`_`[RGBE`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=RGBE_image_format]`_`f.

In digital images, 32-bit sometimes refers to `F33f`_`[high-dynamic-range imaging`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=High-dynamic-range_imaging]`_`f (HDR) formats that use 32 bits per channel, a total of 96 bits per pixel. 32-bit-per-channel images are used to represent values brighter than what `F33f`_`[sRGB`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=SRGB]`_`f color space allows (brighter than white); these values can then be used to more accurately retain bright highlights when either lowering the exposure of the image or when it is seen through a dark filter or dull reflection.

For example, a reflection in an oil slick is only a fraction of that seen in a mirror surface. HDR imagery allows for the reflection of highlights that can still be seen as bright white areas, instead of dull `F33f`_`[grey`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Grey]`_`f shapes.

>>File formats

A 32-bit file format is a `F33f`_`[binary file`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Binary_file]`_`f `F33f`_`[format`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=File_format]`_`f for which each elementary information is defined on 32 bits (or 4 `F33f`_`[bytes`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Byte]`_`f). An example of such a format is the `F33f`_`[Enhanced Metafile Format`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Windows_Metafile]`_`f.

>>See also

• `F33f`_`[History of video games (32-bit era)`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Fifth_generation_of_video_game_consoles]`_`f

• `F33f`_`[Word (computer architecture)`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Word_(computer_architecture)]`_`f

• `F33f`_`[Physical Address Extension`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Physical_Address_Extension]`_`f (PAE)

>>References

`:cite-note-pcmprosise1995-1`!1.`! `F0af`_`[↑`#cite-ref-pcmprosise1995-1-0]`_`f `:citerefprosise1995`aProsise, Jeff (1995-11-07). "16 or 32 Bits: Should It Matter to You?". `*PC Magazine`*. pp. 321–322. Retrieved 2022-11-30.

`:cite-note-sdfebuchanan1997-2`!2.`! `F0af`_`[↑`#cite-ref-sdfebuchanan1997-2-0]`_`f `:citerefbuchanan1997`aBuchanan, William (1997). `*Software Development for Engineers : C/C++, Pascal, Assembly, Visual Basic, HTML, Java Script, Java DOS, Windows NT, UNIX`*. Burlington: Elsevier Science. p. 230. `F33f`_`[ISBN`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=ISBN_(identifier)]`_`f 978-0-08-054137-2. `F33f`_`[OCLC`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=OCLC_(identifier)]`_`f 854975383.

`:cite-note-3`!3.`! `F0af`_`[↑`#cite-ref-3]`_`f `:citerefvenkateswarlu2012`aVenkateswarlu, N.B. (2012). `*Essential Computer and IT Fundamentals for Engineering and Science Students`*. S. Chand Publishing. p. 143. `F33f`_`[ISBN`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=ISBN_(identifier)]`_`f 978-81-219-4047-4.

`:cite-note-4`!4.`! `F0af`_`[↑`#cite-ref-4]`_`f `:citerefpattersonditzel2000`aPatterson, David; Ditzel, David (2000). `*Readings in Computer Architecture`*. San Diego: Academic Press. p. 136. `F33f`_`[ISBN`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=ISBN_(identifier)]`_`f 9781558605398.

`:cite-note-5`!5.`! `F0af`_`[↑`#cite-ref-5]`_`f `*IBM System/360 Model 30 Functional Characteristics`* (PDF). IBM. August 1971. pp. 8, 9. GA24-3231-7.

`:cite-note-6`!6.`! `F0af`_`[↑`#cite-ref-6]`_`f "Motorola 68000 Family Programmer's Reference Manual" (PDF). 1992. p. 1-1. Retrieved 18 January 2022.

`:cite-note-7`!7.`! `F0af`_`[↑`#cite-ref-7]`_`f `:citerefgwennap1995`aGwennap, Linley (16 February 1995). "Intel's P6 Uses Decoupled Superscalar Design" (PDF). `*`F33f`_`[Microprocessor Report`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Microprocessor_Report]`_`f`*. Retrieved 3 December 2012.

`:cite-note-8`!8.`! `F0af`_`[↑`#cite-ref-8]`_`f "ARM architecture overview" (PDF).

`:cite-note-9`!9.`! `F0af`_`[↑`#cite-ref-9]`_`f `*There were also variants of `F33f`_`[UNIX`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=UNIX]`_`f for the 80286`*.

`:cite-note-10`!10.`! `F0af`_`[↑`#cite-ref-10]`_`f This article is based on material taken from 32-bit+application at the `*`F33f`_`[Free On-line Dictionary of Computing`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Free_On-line_Dictionary_of_Computing]`_`f`* prior to 1 November 2008 and incorporated under the "relicensing" terms of the `F33f`_`[GFDL`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=GNU_Free_Documentation_License]`_`f, version 1.3 or later.

>>External links

• HOW Stuff Works "How Bits and Bytes work"

• "Ken Colburn on LockerGnome.com: `*32-Bit Vs. 64-Bit Windows`*". Archived from the original on 2016-03-30.

`c`F0af`_`[↑ Back to top`#top]`_`f`a